Adding an Engine Datasource

Adding a Datasource requires the input of some information that, once entered, cannot be edited.

Procedure

Ensure you have all the required information before proceeding, see Pre-requisite preparation for creation and configuration of a Datasource.

1. From the Settings section of the slide-out navigation pane, select Datasources.
2. Click the Create new datasource button .
3. Enter the datasource name.

This is the name in Campaign Manager's data tree view.

4. Note the following descriptions, and add as required:
   • Engine Server: The machine name on which the Engine project is hosted.
   • Project Name: The Engine Project name as configured in AMC.
   • Date Format: Once correctly configured in AMC this will auto-populate after configuration so should be left blank.
   • Datetime Format: Once correctly configured in AMC this will auto-populate after configuration so should be left blank.
   • Campaign History Database: The database used to store all contact history across all campaign keys. This must be configured before campaigns can be executed.
   • Master Campaign Table: This table will contain 1 row per campaign on the system across all Campaign Keys in this Datasource. It is required before any campaigns can be executed. If left blank, the system will allow editing after Datasource creation. Once named it cannot be changed.
   • Archive Path: This directory, on the engine server is where all of the state table archives are stored.

In Campaign Manager, there are hidden state tables which track members of the campaign audience, their track, inclusion, etc. Once a campaign has been completed there is very little need for these tables to remain (except possibly for attribution processing). You are able to remove the state tables from completed and cancelled campaigns from the User Interface by clicking the Remove State button. The state table is then removed if all of the campaign history has been processed. It is also possible to automate this process by entering an archive path. The automated process to remove state tables contains two stages:

The archive stage, in which the campaign state table of completed and cancelled campaigns is exported to a text file in the location defined in the Archive Path. These records are then removed from the engine repository. The purge stage, in which the text file created in the archive stage is deleted. This two-step process gives the opportunity, if needed, to restore the state table into engine for analysis.

When a new Datasource is created if the archive path field is left blank it will auto populate with the full path pointing at an archive folder within the Engine repository. This can be edited after Datasource creation.

If the archive path is configured the 'State Table Archive Days' and 'State Table Archive Purge days' also need to be configured.

• State Table Archive Days: number of days after which the state table will be archived to a text file in the defined location. If left blank a default of 5 will be used. This can be edited after Datasource creation.
• State Table Archive Purge Days: Number of days the campaign state table text data will stay in the archive directory before it is deleted. If left blank a default of 10 will be used. This can be edited after Datasource creation.

• System Data Path: The path to the segregated system owned data, campaign state, tactic output and metrics. This path can only be created via AMC on creation of an Engine Project. This section is a reference to that value. For more information refer to: Best Practice Guide - Minimizing Downtime with AB Repository Switching.

5. Click Save.

Once completed, the Engine repository can be viewed in Campaign Manager for those users who have access.

• Datasources
  • Prerequisites for creating and configuring Datasources
  • Adding an Engine Datasource
  • Generate Campaign Test History Setting
  • Editing an Existing Datasource
  • Disabling or Enabling a Datasource
  • Allocating Campaign Settings to an Engine Datasource
  • Configuring Access Permissions to a Datasource
  • Applying Engine Row and Column Permissions
  • Setting Engine Security